Add xarray upper bound to avoid v2024.02.0
#108
Conversation
navidcy
changed the title
xarray upper boundxarray upper bound to avoid v2024.02.0
|
The root of this is xESMF needing to upgrade to look for |
|
oh I see! is there a better solution than adding a compat entry for xarray? |
|
If you can comment on the issue I opened in xarray it might be helpful. Perhaps that needs to close then.. |
No, I think this is still the way to go. |
OK, cool! |
|
But I wonder if there's a way to remind us to unpin when there's a new xESMF release... |
|
you hope that because we mentioned the xESMF issue we'll now get notifications when things update there and we'll see when it's resolved, right? |
|
I actually subscribed to the issue to make sure. |
|
Shall we merge this you reckon? |
After the latest xarray release errors started appearing in the CI. See, for example, https://github.com/COSIMA/regional-mom6/actions/runs/7957078139/job/21719091616#step:7:226
See pydata/xarray#8769
Adding an upper bound in
pyprojectto preclude the xarray v2024.02.0 resolves the issue for now until a patch release comes out from xarray.